Detecting associates

ABSTRACT

Detecting, for a content item, associated preference events is disclosed. For the content item, a plurality of preference events from a plurality of users is received. The received preference events are accumulated. Associated events are detected. The effect of the events is reduced when assigning a status to the item.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent application Ser. No. 12/283,139, filed Sep. 8, 2008 and entitled DETECTING ASSOCIATES, which claims priority to U.S. Provisional Patent Application No. 60/967,910, filed Sep. 6, 2007 and entitled DETECTING ASSOCIATES AND AUTOMATICALLY ADAPTING THRESHOLDS, all of which are incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

Popular content repositories, review and voting sites, and other social collaborative networks generally contain a vast amount of content. Such sites typically encourage users to rate the content (including photographs, news stories and journal entries, videos, products and other items, and services, etc.) to aid other users in locating interesting or otherwise desirable content and avoiding content that may not be of interest.

Unfortunately, unscrupulous individuals may attempt to leverage the popularity of such sites for financial gain such as by directing traffic to advertising and other self promotional material (e.g. spamming). They may also attempt to unfairly wage “smear campaigns” against legitimate content, such as competitors' products. One way of engaging in either of these behaviors is to band together with other users (whether they are other individuals or additional, fictitious users under the control of a single user) to rate content in a concerted manner for mutual benefit.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1A illustrates an embodiment of an environment for collecting and managing content contributions.

FIG. 1B illustrates an embodiment of an interface to a preference system.

FIG. 2 is a flow chart illustrating an embodiment of a process for receiving a story submission.

FIG. 3 is a flow chart illustrating an embodiment of a process for receiving a story submission.

FIG. 4 illustrates an embodiment of a story permalink.

FIG. 5 illustrates an embodiment of an interface to a preference system.

FIG. 6 illustrates an embodiment of an interface to a preference system.

FIG. 7 is a flow chart illustrating an embodiment of a process for recording a preference for a content contribution.

FIG. 8A illustrates an embodiment of a visualization interface.

FIG. 8B illustrates an embodiment of a visualization interface.

FIG. 8C illustrates an embodiment of a visualization interface.

FIG. 8D illustrates an embodiment of a visualization interface.

FIG. 9 illustrates an embodiment of a visualization interface.

FIG. 10 illustrates an embodiment of a visualization interface.

FIG. 11A illustrates an embodiment of a visualization interface.

FIG. 11B illustrates an embodiment of a visualization interface.

FIG. 11C illustrates an embodiment of a visualization interface.

FIG. 12A is an example of a content contribution.

FIG. 12B illustrates an embodiment of an interface to a preference system.

FIG. 12C illustrates an embodiment of an interface to a preference system.

FIG. 13A illustrates an embodiment of an interface to a preference system.

FIG. 13B illustrates an embodiment of an interface to a preference system.

FIG. 14 illustrates an embodiment of an interface to a preference system.

FIG. 15 is a flow chart illustrating an embodiment of a process for detecting associates.

FIG. 16 is a flow chart illustrating an embodiment of a process for promoting content.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or communication links. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. A component such as a processor or a memory described as being configured to perform a task includes both a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. In general, the order of the steps of disclosed processes may be altered within the scope of the invention.

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

FIG. 1A illustrates an embodiment of an environment for collecting and managing content contributions. Users, such as user 104, submit content (hereinafter a “story contribution” and a “third party news article contribution”) to preference system 102. In the example shown, content is submitted in part by providing to preference system 102 the uniform resource locator (URL) of a story, such as a story found on web page 106.

Preference system 102 includes a web module 108 that provides typical web server functionality such as serving website 116, capturing user input, and providing Really Simple Syndication (RSS) feed (110) support. In the example shown, web module 108 is an Apache HTTP server that supports running PHP scripts. Web module 108 is interfaced with a database 112, such as through a MySQL database backend.

As described in more detail below, users are made aware of the submitted content through website 116 and features such as RSS feeds. In addition to providing a link to the content (e.g., a hyperlink to web page 106) and information such as a summary of the story and the date and time it was submitted, website 116 permits users to indicate their preferences for the content by making a variety of interactions. For example, users can “digg” a story to indicate their like of its content, “bury” a story to indicate problems with the content, and may also take other actions such as commenting on the content. These actions (including the initial submission of the content contribution) are referred to herein collectively as “preference events.”

Whenever a preference event occurs (e.g., whenever a user submits, diggs, buries, or comments on content), the event is recorded in database 112 along with associated information such as the identity of the user and a time/date stamp. As described in more detail below, information recorded in database 112 is used in a variety of ways, such as in conjunction with visualization tools that query database 112 and/or make use of data extracted from database 112.

In some embodiments, a promotion engine 118 is included. As described in more detail below, promotion engine 118 makes determinations such as what content should appear in various sections of website 116. For example, content that appears to be popular may be “promoted” by promotion engine 118 by being displayed in a prominent location on the main page of website 116 for some period of time.

Cohort detection module 120 is configured receive information from database 112 and determines groups of cohorts, e.g. as a batch process. As described in more detail below, in some embodiments when content is evaluated for promotion (e.g., by the promotion engine), the promotion engine determines whether a threshold number of cohorts (e.g., at least 4/8 of those individuals in a group) dugg the content. If so, it reduces the impact of their actions, as appropriate.

In some embodiments, the infrastructure provided by portions of preference system 102 is located on and/or replicated across a plurality of servers rather than the entirety of preference system 102 being collocated on a single platform. Such may be the case, for example, if the contents of database 112 are vast and/or there are many simultaneous visitors to site 116.

FIG. 1B illustrates an embodiment of an interface to a preference system. The example shown is an implementation of a portion of website 116, as rendered in a browser. A user, known as “Alice” is logged into site 116. Interface 150 includes a sidebar 152 that provides access to various system services. For example, by selecting region 154 of sidebar 152, Alice is presented with an interface that permits her to view her profile and manage account settings such as her current email address and password; view previous preference events she's taken (her “history”); and access friend-related features described in more detail below. Region 156 provides an indication of whether Alice has any messages and will present her with an interface to a message system (such as a mailbox) if selected. As described in more detail below, by selecting region 158, Alice will be presented with an interface through which she can submit a news story for inclusion on system 102.

Region 160 displays a list of categories into which news stories are grouped. If “View All” is selected, stories from all categories will be displayed in story window 164. As shown, the “Technology” category is selected. In some embodiments, visual indications of what category is selected are presented. In the example shown, the selected category is highlight (represented here by stippling) at 166, and the title of the category appears above story window 164 at 168. In some embodiments, Alice can configure which topics are available to her on site 116. For example, if Alice dislikes Sports, she can configure interface 150 to never show her any sports-related stories, even when viewing using the “View All” option.

Story window 164 typically includes one or more story entries 170. In the example shown, a story entry includes the title of a story, as well as other associated information, such as who submitted the story and when, the external URL of the story, the category to which the story belongs, and a summary of the story. As described in more detail below, links are provided to the story directly (such as by clicking on the title), as well as to an area of site 116 associated with the story, referred to herein as the story's permalink. For example, by clicking on the comments link (176) of the story, Alice will be presented with the comments portion of the permalink described in more detail below.

Story entry 170 also includes a problem reporting region 178. Users may report problems for a variety of reasons. For example, the first story entry and the third story entry shown describe the same news—scientists superheating a gas. Alice has selected the problem, “duplicate” story, from problem reporting region 178. As described in more detail below, this is one form of burying a story. In some embodiments, buried stories are displayed differently, or removed entirely from the user's interface. In the example shown, once a story is buried, it is greyed out, represented here by stippling (180).

As described in more detail below, each story has one or more scores associated with it. In the example shown, the “digg” score (172) for each story is displayed, as is an interactive region beneath the score (box 174) that allows a user to “digg” the story. The first story has been dugg 237 times, but has not been dugg by Alice. As described in more detail below, if Alice were to select region 174, a variety of actions would be immediately taken, including increasing the digg score of the story and updating the region's text from “digg it” to “dugg!” as shown in region 182.

Alice is currently viewing a “promoted stories” (184) view of story window 164. This means that all of the stories presented to Alice on the current view of the interface have exceeded a promotion threshold. One example of a promotion threshold is the raw number of diggs. Other requirements/factors may be used for thresholding in addition to or instead of a digg score, such as requiring that a certain amount of time elapse between story submission and story promotion, the speed with which stories are being dugg, information associated with users that have dugg the story, etc. Because some threshold of users must agree that a story has merit before being promoted, stories shown in promoted view 184 are unlikely to contain spam or otherwise be inherently inappropriate for Alice's viewing.

In some embodiments, different thresholds are used for different stories, such as for stories in different categories. For example, the promotion of a math related story may only require 100 diggs whereas a story about the president may require 500 diggs. Techniques for promoting content are described more fully below.

If Alice selects the upcoming stories tab (186), only stories which have not yet met the appropriate threshold will be displayed. For example, newly submitted stories which have not yet been “dugg” by a sufficient number of people will be presented by selecting tab 186. In some embodiments, if a story languishes in the upcoming stories pool for more than a certain period of time without receiving a sufficient digg score to be promoted (e.g., for a week), the story is removed from the pool and can only be found via its permalink or through a search. In some embodiments, such stories are deleted from database 112. Such stories are typically indicative of spam, inaccuracies, and old news. Similarly, if enough users bury a story, the story may be removed from the pool and/or database 112.

In other embodiments, other views of stories may be presented as applicable, such as a view that unifies both the promoted and the upcoming stories. In the example shown, because Alice has selected the “Technology” category (166), only technology related stories are presented in the promoted stories (184) and upcoming stories (186) views. Similarly, the topics of the presented stories (e.g., “Math,” are all subtopics of Technology). In some embodiments, the information presented with the story entry may vary, such as from topic to topic. For example, if Alice selected “View All” at 160, the listed topic may be the top level category to which the story belongs (e.g., “Technology”) or include a drilled down description (e.g., “World News-Canada-Elections”).

As described in more detail below, portion 162 of interface 150 displays the recent activities (preference events) of Alice's friends. For example, in the last 48 hours, Alice's friends have submitted two stories, dugg twelve stories, and commented on sixteen stories, as reflected in dashboard 162. Of the twelve stories her friends have dugg, four of the stories have not yet been promoted. In some embodiments, assorted visual cues of her friends' activity are presented throughout website 116. In the example shown, stories dugg by Alice's friends are notated by a banner (184) placed across the digg score. In other cases, other cues may be used, such as by changing the color of the story, and/or interactive behavior such as playing a sound or showing the friend's avatar icon when, for example, Alice's cursor hovers over a story dugg by a friend.

Region 188 displays a list of tools, such as visualization tools, that Alice can use to view and interact with content and/or preference events.

Story Submission

FIG. 2 is a flow chart illustrating an embodiment of a process for receiving a story submission. This process may be implemented on preference server 102. In the example shown, the process begins at 202 when information associated with a story is received. For example, in some embodiments at 202, information such as the URL of a story and a summary of the story located at that URL is received.

At 204, one or more checks are performed. As described in more detail below, examples of checks include checking to make sure the URL is valid and does not, for example, contain a typo; checking for duplicate stories; determining whether the story submission appears on a blacklist or is otherwise to be blocked; determining whether the story is being submitted by a blacklisted user; determining whether the story is being submitted by an anonymous proxy, etc. At 206, it is determined whether the story should be accepted.

In some embodiments, if the story submission fails any of the checks performed at 204, the story is rejected at 210. In some embodiments, a threshold is applied to whether or not a story is accepted at 208. For example, a story that appears to be a duplicate may be flagged for review by an administrator, may be provisionally marked as a potential duplicate, may be accepted so long as no other checks are failed, etc. In some embodiments, the identity of the submitter is taken into consideration when determining whether to accept a story. The decision of whether to accept the story may be based at least in part on factors such as the length of time the user has been a registered user of site 116, whether the user has previously submitted inappropriate content, and/or a score assigned to the user.

Typically, the information received at 202 is received through a web interface, such as a story submission form that can be accessed, by selecting region 158 of interface 150. Other methods of submission may also be used, as appropriate. For example, an external website, such as a user's blog could be configured to provide an interface to server 102. Submission may also be automated, such as by syndicating a news feed to a story submission component executing the process shown in FIG. 202. As described in more detail below, submissions of the information received at 202 can also occur through the use of an application program interface (API), browser plugin, etc.

FIG. 3 is a flow chart illustrating an embodiment of a process for receiving a story submission. In the example shown, the process is implemented on preference server 102 and is an example implementation of the process shown in FIG. 2. The process begins at 302 when an indication that a story is being submitted is received. Suppose Alice wishes to submit a story. When she selects region 158 of interface 150, server 102 is notified at 302.

At 304, it is determined whether the submitting user is logged into site 116. If not, the user is presented with a page at which he or she can create an account or log in to an existing account. After completing registration and/or logging in, the user is directed back to the story submission interface (not shown).

A logged in user, such as Alice, is then presented with an interface through which a story may be submitted such as a web form. At 308, a URL is received, such via Alice entering the URL into the form.

System 102 maintains a block list that includes URLs that, e.g., have been reported by administrators as spam sites, fraudulent sites, etc. If a threshold number of users report a story (such as through region 178 of interface 150), the story may be automatically added to the block list. At 310 it is determined whether the URL is present on the list of blocked URLs. In some embodiments, instead of or in addition to maintaining a list of block URLs, system 102 checks for blocked URLs in conjunction with a third party, such as a commercial anti-spam registry. If the submitted URL appears on the blocked list, the user is presented with an error at 312. In various embodiments, the error indicates to the user the problem with the URL, such as that the URL belongs to a known spammer. In such cases, the user may be presented with the option of challenging the block. In other embodiments, a user submitting a blocked URL is not told why the URL is blocked, or may not be told that the URL is blocked at all. For example, a spurious “system configuration” error may be presented to the user to help minimize attempts at circumventing checks.

At 314, it is determined whether the URL can be reached. One way of performing this check is to make use of a tool such as curl or wget. If the URL cannot be reached, for example because of a typo (e.g., HTTP Status Code 404) or because accessing the URL requires a login/password (e.g., HTTP Status Code 401), the user is presented with an error at 316. In various embodiments, the user is permitted to revise and resubmit a failed URL without having to restart the process at 302.

Duplicate checking is performed on the URL at 318. In some embodiments, the check performed looks only for exact matches of the URL. In other embodiments, fuzzy or other matching is applied.

If it is determined that the submitted URL is a duplicate of, or similar to a URL previously submitted to server 302, at 320 the user is presented with a list of the previously submitted story or stories. In some cases, the new story submission is a duplicate of an existing story submission. In other cases, however, the stories may be distinct, despite sharing a common URL. Such may be the case, for example, with a corporate website that always posts new press releases to the same URL, such as “www.company.com/news.html.” Suppose Alice submits a URL that is already stored in database 112. At 320 she is asked to compare her story against the other story or stories submitted under that URL (324). For example, the interface may present to her a list of the existing stories matching her submitted URL in a format similar to story window 164 shown in FIG. 1B. If the story she wishes to submit has already been submitted, she can digg the existing story (326), rather than submitting a duplicate. If her story is not a duplicate, she can continue with the submission. In various embodiments, considerations such as the sophistication of the user determine whether an exact duplicate URL will be permitted or whether the user will be forced to digg one of the stories presented on the duplicate list instead of submitting the new story submission.

At 322, the user is prompted to supply additional information about the story submission, such as the story's title, a summary of the story, and to which category or categories it belongs. In some embodiments, the information collected at 322 is received at the same time that the URL is received (308) and portion 322 of the process shown in FIG. 3 is omitted.

At 328, additional checks are performed on the story. For example, a spam story may escape detection at 310. Such may be the case if the spam was recently created or is an attempt to unscrupulously drive traffic to a previously legitimate page and is not already present in a blacklist. One check that can be performed at 328 includes applying spam detection techniques to the text located at the submitted URL and/or the title or summary provided by the user. Additional checks may also be employed in addition to or instead of spam checks at 328. For example, a determination may be made of whether the submitter (e.g., Alice) is connecting to site 116 via an anonymous proxy. If it is determined at 328 that the submission is spam or should otherwise not be accepted, at 330, the submission is rejected. In some embodiments, the submission is “silently” rejected—the user is shown a “successful” dialogue when in fact the story is rejected. In other embodiments, the user is presented with an error, such as the error presented at 312.

Additional duplication checks are performed on the story at 332. In some embodiments, the submitted title and summary of the story are compared against the titles and summaries of stories already submitted to server 102. In some embodiments, the page is crawled and a full text match (such as a MySQL full text search) is performed against the submitted story and previously submitted stories. In such a case, database 112 is configured to store at least portions of the crawls in addition to information associated with the story. If it is determined that the story is a potential duplicate, at 334 the user is presented the option of digging the story (336) or submitting it anyway.

When a story is accepted at 338, an entry for the story submission is created in database 112. Information such as the submission time and the user who submitted the story are stored and counts associated with the story, such as its digg score, are set to zero. The story becomes accessible in the upcoming stories view (e.g., 186 of FIG. 1B).

Information in one or more tables 114 is also updated to include information associated with the new story, for example for use in conjunction with searching, and with visualizations discussed in more detail below. Additionally, information associated with the submitting user is modified as appropriate. For example, a count of the number of stories submitted by the user is incremented, and the story is made available in areas such as the user's profile and the profile areas of the user's friends, if applicable.

As described in more detail below, a permalink for the story can be accessed by visitors to site 116 and contains content assembled dynamically from the information stored in database 112. In system 102, the permalink's URL is created by stripping disallowed characters (such as punctuation) from the submitted story's title and appending digits as necessary to avoid collisions. So, for example, if Alice's submitted story were titled “New Species of Bird Discovered,” once accepted at 338, information associated with the submitted story would be accessible at the URL, “http://www.digg.com/science/New_Species_of_Bird_Discovered.html.”

Also at 338, if the user has specified blogging information, such as a username and password of an account on a blogging service, the submitted story is posted to the user's blog. Information such as the summary and/or title of the story can be automatically copied into the blog submission and/or edited by the user prior to submission. For example, if Alice has specified the details of her blog account in her profile (reachable by selecting portion 154 of interface 150), when submitting story submissions, she can specify whether she'd like the story to also appear in her blog. If Alice has not configured her blog settings, the ability to blog can be greyed out, hidden, and or explained at 338, as applicable.

Recording and Reflecting Preference Events

FIG. 4 illustrates an embodiment of a story permalink. The example shown is an implementation of a portion of website 116 as rendered in a browser. Story 402 was recently submitted to server 102 (26 minutes ago), through the process depicted in FIG. 2. When Alice visits the permalink of story 402, topic region 160 of sidebar 152 automatically expands and highlights the topic with which story 402 is associated (in this case, “Science”). The story was submitted by David, who also dugg the story. Alice has David listed under her profile as her friend. As a result, the digg count includes a visual indication 404 that story 402 was dugg by a friend. In some cases, Alice and David know each other and have each other, mutually, on their list of friends. In other cases, the relation may be one sided. For example, David may be a columnist or famous personality whose opinion Alice values.

The digg score of story 402 is currently two (404) and the story has not met the threshold(s) required for the story to be promoted out of the “upcoming stories” area.

In the interface shown in FIG. 4, Alice can click digg box 406 to indicate her preference for the story. In some embodiments, additional actions are taken when Alice diggs a story. For example, if she has configured her blog settings, Alice can specify that stories that she diggs be posted to her blog as she diggs them. Similarly, Alice can configure her personal website (e.g., with a JavaScript) to automatically syndicate recent activities taken in response to stories.

She can report a problem with the story (bury it) by selecting an option from problem dropdown 408. Story reporting options include “duplicate” story (to report that story 402 is a duplicate of another story), “bad link” (to report that the link to the full text of the story is defective), “spam” (to indicate that the story is fraudulent or spam), “inaccurate” (to indicate that there are factual problems with the story), and “old news” and “this is lame” to indicate that the story is not newsworthy. In some embodiments, bury events are anonymous site wide and are not replicated, for example, in a user's publicly accessibly digging history. One reason for this is to minimize the chances of a “flame war” occurring, for example, when a well known user negatively rates a story or comment.

As described in more detail below, region 410 displays comments that users have made about story 402. Thus far, a total of five comments have been left about story 402, two of which were left by Alice's friends. Alice can submit comments by entering information into region 412 of FIG. 4.

In region 414, Alice is currently viewing a list of all the users who dugg story 402. Suppose David is Alice's friend, but Legolas is not. If Alice selects friends tab 416, the view in region 414 will change to show only David's name and avatar icon.

In region 418, Alice is currently viewing a list of the users who have blogged story 402. Charlie is the only person who has blogged the story so far and he is not Alice's friend. Therefore, if Alice were to select friends tab 420, no names would be shown.

Alice can submit this story to her own blog by entering in optional text in region 422 and selecting region 424. Alice can email the story to one or more addresses by entering them into region 426 and selecting region 428.

As shown, all of the information associated with a particular story (e.g., title/summary of the story, digg score, comments, who has blogged the story, etc.) is displayed on a single page. In other embodiments, the information is presented across multiple pages, such as with a tabbed view with one or more tabs for each component.

FIG. 5 illustrates an embodiment of an interface to a preference system. The example shown is an implementation of portion 410 of website 116, as rendered in a browser. In the example shown, Alice is viewing comments associated with a story. The story currently has eight comments (502), sorted by date. A threshold of −4 diggs or higher has also been applied (518). Thus, comment 516, which has been buried 75 times, is hidden. In the example shown, only the header of a buried comment is displayed, along with a link to reveal the hidden comment (522). Additionally, the header of comment 516 is greyed out to help a user visually distinguish between buried and nonburied comments.

Comment 504 was written by Bob, one of Alice's friends, as was comment 506 (written by David). In this example, comments written by friends are distinguished from other comments, such as through having a differently colored header. Comments dugg by friends are also distinguished. Thus, while CharlieB is not Alice's friend, his comment (508) is distinguished because it was dugg by Bob, who is Alice's friend, as also indicated by the inclusion of Bob's name and a star on the header of comment 508. The number of comments left by and/or dugg by her friends are indicated at 514.

In the example shown, Bob has written an informative comment, which 18 people have dugg. If desired, Alice can digg or bury Bob's comment by selecting the appropriate icon at 520. In the example shown, the digg icon is a green thumb pointing up. The bury icon is a red thumb pointing down. As described in more detail below, if Alice selects one of the icons, Bob's comment score is immediately updated and the thumbs are greyed out to indicate to Alice that she's already registered her preference for Bob's comment.

Suppose Alice finds comment 510 to be off topic or otherwise unhelpful. If she chooses to bury the comment, in the example shown, a variety of changes will occur in the interface immediately. The comment score for comment 510 will decrement by one point. Additionally, comment 510 will collapse down to just the header, which will grey out. If Alice finds the poster of the comment, Legolas, a sufficient nuisance, she can block him by selecting block icon 524. In this example, if Alice selects the block icon, she will never be shown any content from Legolas again, site-wide, unless she later chooses to unblock him, such as through settings in her profile. Thus, by selecting block icon 524, Alice will not see comments made by Legolas, stories posted by Legolas, etc., unless and until she chooses to unblock him.

In some embodiments, if enough people bury a comment, the comment is removed from the site and/or reported to an administrator. Similarly, if enough people block a user, in some embodiments, the user is reported to an administrator and/or banned from accessing site features.

If desired, Alice can submit one or more comments of her own. For example, she may reply to an existing comment by selecting the reply button associated with the comment (526), or create a new comment by submitting text through region 528. In some embodiments, Alice is given a portion of time during which she may edit the comment, such as within five minutes of submitting the comment.

As described in more detail below, when Alice submits or diggs a comment, that preference event is recorded in database 112, her profile and the profiles of her friends are immediately updated, and associated RSS files are updated.

FIG. 6 illustrates an embodiment of an interface to a preference system. The example shown is an implementation of a portion of website 116 reached by selecting region 154, as rendered in a browser. In this example, Alice is viewing her profile (hereinafter “interface 602”), which has been subdivided into several tabbed views (604-610). A profile provides access to a variety of information, some of which may be publicly viewable, and some of which may be kept private. For example, Alice can change account settings such as specifying her email address and password by selecting portion 604 of interface 602. Visitors to Alice's profile will be presented with a subset of the information available to Alice. For example, while Alice sees tab 604 being labeled “Profile+Settings,” a visitor to Alice's profile would see tab 604 as leading to Alice's “Profile” only. Similarly, tab 608, which by selecting allows Alice to add and remove friends, is only available to Alice and is hidden from visitors to her profile. Alice can also add friends by visiting other users' profiles and selecting an “add this user as my friend” option located in the profile.

Alice has currently selected to view her friends' history by selecting portion 610 of interface 602. The information presented can be further customized by selecting from subsets of information. For example, if Alice selects portion 620 of interface 602, she will be presented with a listing of all of the stories that have been dugg by at least one of her friends. If she selects portion 622, she will be presented with a list of stories that have been dugg by at least one of her friends but have not yet been promoted. If she selects portion 626, Alice will be presented with a list of stories submitted by her friends, and by selecting portion 628, Alice will be presented with a list of stories that have been commented on by her friends. Other information (not shown) may also be presented in other embodiments, such as a list of comments that Alice and/or her friends have dugg.

In the example shown, Alice has selected to view stories “agreed on” by her friends (624). Each of the stories listed in this view have been dugg by at least three of Alice's friends. In various embodiments, Alice can configure the threshold and specify such information as the number of friends (or total number of diggs) required for a story to be agreed upon and/or define particular individuals whose digg is necessary for a story to be considered agreed upon, keywords that must be present in the story, etc. By making use of the “agreed on” view, Alice can readily discern the most important stories, even if she has thousands of friends. (I.e., if she sets the threshold to “agreed on by at least 10 friends,” and has 1000 friends, the number of stories she is presented with is likely to be manageable and especially relevant or interesting.)

Region 616 of interface 602 indicates that four of Alice's friends have dugg story 632. Alice can also see which of her friends have dugg story 632 by hovering her input device over the digg score box of story 632. In some embodiments, Alice can interact with region 616, such as by being presented with a dialogue that offers to send an email to all of her friends listed in the region.

By selecting portion 606 of interface 602, both Alice, and visitors to Alice's profile will be presented with Alice's history in a format similar to that currently shown, but limited to activities taken by Alice. Additionally, Alice may “undigg” stories and comments that she previously dugg by visiting her history.

All of the views described in conjunction with FIG. 6, such as stories “Agreed On” by Alice's friends can by syndicated as RSS feeds by selecting RSS link 614 on the appropriate page view. In some embodiments, profile visitors (including Alice) are presented with the option to search (630) all of site 116 for content (634), search Alice's diggs for content (636) and/or search diggs made by Alice's friends for content (638).

When a user takes certain actions, such as digging a story or burying a comment, the results of that action are reflected immediately, without the user being directed to a “success” page or the appearance of, e.g., a page refresh occurring to the user. For example, suppose Bob has listed Alice as his friend. Whenever Alice submits a new story, that new story immediately appears on Bob's “Friends—Submitted” list and is written to the associated RSS file. Similarly, whenever David comments on an article, that fact is immediately reflected under Alice's tab 628 as shown in FIG. 6. As described herein, pages served by web module 108 include Asynchronous JavaScript and XML (Ajax) components. Other techniques may also be used to dynamically update site 116 as rendered in a browser as appropriate.

FIG. 7 is a flow chart illustrating an embodiment of a process for recording a preference for a content contribution. The process begins at 702 when an indication that a preference event has occurred is received. For example, when Alice selects digg box 406 shown in FIG. 4, her preference is received at 702. Other examples of preference events include submitting a story, burying a story, and commenting on a story. At 704, the preference event is associated with the content contribution and any associated scores are updated as applicable. For example, at 704, Alice and story 402 are linked in database 112 and the digg score of story 402 is increased in database 112 from two to three. At 706, information associated with the user's profile is updated. For example, as described in more detail in conjunction with FIG. 6, views of Alice's digging history (including the friends views of users who have listed Alice as a friend) are updated to include the dugg story and an indication that Alice dugg it. Any RSS files associated with her profile and the profiles of those who have her listed as a friend will also be updated as appropriate.

Visualizations

FIG. 8A illustrates an embodiment of a visualization interface. The example shown is an implementation of a portion of website 116 as rendered in a browser. In this example, interface 800 (also referred to herein as the digg “spy” interface and a “ticker” interface) is configured to present a real time visualization of preference events occurring on preference system 102.

In the example shown, a user such as Alice can specify which stories to spy on. For example, she can spy on all stories (802), stories which have not yet been promoted (804), or just promoted stories (806). Further specification of a subset of stories can also be applied, as applicable. For example, in various embodiments, a user can specify a key word that must be present in all stories being spied upon, and/or spy on stories in specified categories (not shown), and/or spy on events taken by friends only.

Additionally, a user can specify the types of preference events to be spied upon. In the example shown, Alice has checked (would like to see) all types of activity—new story submissions (indicated by icon 810), diggs (indicated by icon 812), buries (indicated by icon 814), and comments (indicated by icon 816).

One way of implementing the visualization shown in FIG. 8A is as follows. As a preference event occurs, it is recorded in database 112. Maintained within database 112 are a main database table and four smaller tables 114—one for each type of event. The event is also recorded (either concurrently with, or on a periodic basis such as by way of an update function) in the respective smaller table that corresponds with the event. In some embodiments, filtering is applied so that, for example, only commenting of registered users is recorded in the comment table but all commenting is recorded in the main table. A flag in the main database (e.g., a “do not report this to spy” flag) can also be set that indicates whether information associated with a particular story or user should be copied to the smaller tables 114. Alice is a typical user whose diggs are recorded in the main database table, as well as the smaller table that records only diggs.

When Alice first visits interface 800 with her browser, and on a recurring basis after that (such as every 20 seconds, or whenever the pool of events is running low), batches of information are retrieved from server 102 in a scope commensurate with the options selected (which documents to spy on and for which activities). Specifically, the most recent content from each of the smaller tables 114 is retrieved from server 102 and stored locally, such as in Alice's browser. Asynchronous JavaScript and XML (Ajax) components in interface 800 cause the information to displayed to Alice, for example, at a rate of one event per second, depending on which information she would like to view. In some embodiments, Alice can control the speed of the display, such as through playback controls 808.

In some cases, such as with heavy digging activity, there may be sufficiently more than 20 diggs occurring site-wide during the twenty second interval between the times that Alice's browser fetches a new batch of digging information. Thus, after twenty seconds have elapsed, system 102 may have recorded 200 digg events—significantly more than the 20 digg events that Alice periodically fetches. In some embodiments, only the most recent 20 actions are fetched. Thus, every twenty seconds, Alice requests the 20 most recent events and will never see any intervening events.

In other embodiments, the number of events fetched adjusts in accordance with the speed with which the events are occurring. In such case, all of the events are fetched and the rate with which they are displayed is sped up (showing one every tenth of a second if there are 200) or slowed down (showing one every five seconds if there are only four) as appropriate. In some embodiments, a sampling of activity is taken throughout the period so that if 200 events occur during the 20 second interval, a random sample of 20 will be supplied to Alice's browser.

In the example shown in FIG. 8A, Alice has been viewing interface 800 for six seconds. Six events (830-840) are displayed, with the mot recent (840) displayed at the top. As a new event is displayed, the already displayed events are pushed down the display. Thus, for example, at time t1 (when Alice first began watching the interface), only event 830 was presented. At time t2 (one second later), event 832 was displayed above event 830, pushing event 830 down the screen. At time t3 (one second after time t2), event 834 was displayed, pushing events 832 and 830 each down one position, respectively.

By consulting the column descriptions (842), Alice can see that event 830 was a submission of a new story (818), titled “Scientists Discover New Type of Bird” (822), that the story was submitted by CharlieB (824)), and that the story is currently unpromoted (826) with a digg score of 1 (820). When event 832 appears in the display at time t2, Alice can see that event 832 was a comment by Legolas on a story titled “How to Make a USB Powered Alarm Clock” that currently has a digg score of 33 and has been promoted out of the upcoming stories queue. At time t3, Alice can see that David posted a new story titled “New Species of Bird Discovered.” At time t4, David's story was reported as being a duplicate story (828). The identity of a user burying something is not shown. Instead, only the reason for the bury (such as duplicate story, inaccurate story, old news, etc.) is shown. In other embodiments, other information can be displayed, as applicable.

In FIG. 8A, the displayed digg count for a story is shown as what it was at the time the event occurred. Thus, when event 838 (a digg of “How to Make a USB Powered Alarm Clock” by Bob) occurs, the digg count of the story is shown as 33. The next time the story is dugg, the updated score is shown, such as when event 840 occurs. If the digg events are happening sufficiently quickly that some of them are not displayed to Alice, she might see gaps between the scores. For example, if 50 diggs of the alarm clock story occur in the next few seconds, Alice may only be presented with the most recent digg and the updated total (e.g., 83 diggs).

FIG. 8B illustrates an embodiment of a visualization interface. The example shown is an implementation of a portion of website 116 as rendered in a browser being used by Alice. In this example, interface 850 (also referred to herein as a “stack” interface/visualization) is configured to present a visualization of newly submitted stories. After a new story is submitted, such as through the submission interface described in conjunction with FIG. 3, it is represented in interface 850 as a green square falling from the top of the screen, and landing at the bottom. Any stories already existing on the page (e.g., 858, 882, 856, and 854) are shifted to the left to make room for the new story (852). In some embodiments, stories are removed from the left side to make space for stories on the right side. In other cases, the width of the stories shown decreases to accommodate more stories as they are added to the interface. The length of time that a user has been viewing interface 850 is shown here as a timeline, with the time that Alice first started viewing interface 850 on the left (866) and the current time on the right (868).

In the example shown, eleven new stories have been submitted since Alice began viewing interface 150. Statistical information such as the number of stories submitted, the rate with which they are being submitted, etc., is indicated at 870. As preference events associated with the stories displayed in interface 850 occur, they are also indicated in interface 850. For example, when a story is dugg, the event is represented by a digg icon, such as the one shown at 812 in FIG. 8A falling from the top of the screen and onto the heap of the corresponding story, increasing the size of the heap if it is a digg, and decreasing the size of the heap if it is a bury. For example, at 860, a digg of story 858 is shown falling down onto the story's graphical representation and will increase the height of the story box when it lands. A variety of indicators, such as colors and avatars can be used to indicate the occurrence of preference events in addition to or instead of the icons shown in FIG. 8A.

At 864, a bury of story 882 is shown falling down onto that story's graphical representation and will decrease the height of the story box when it lands. In the example shown, the bury is indicated by the bury icon shown at 814 in FIG. 8A. The identity of the user burying the story is not shown (as it can be in the case of other preference events), but by hovering her mouse over bury 864, Alice is shown a dialogue that includes the reason that the bury was submitted (e.g., “spam”).

In some embodiments, additional elements are included, such as the animation shown at 880 (of a missile about to strike heap 882), and indications of who is taking the action. For example, diggs 860 and 862 are being performed by friends of Alice. She is alerted to this fact by bubbles accompanying the digg action being performed that indicate their names and/or avatars. The look of interface 850 can be skinned in some embodiments—Alice can specify that she desires the interface to have a militaristic theme, such as in the example shown, or other themes, such as ones in which animals “eat” stories or multiply.

The relative popularity of newly submitted stories is indicated by the relative heights of the stories shown in interface 850. For example, story 884 is a very popular story, while story 856 is not.

In the example shown, only newly submitted stories are shown. Interface 850 can also be scoped to represent other portions of activity. For example, Alice can specify that she wants to observe only actions taken by her friends (or groups of her friends), but across all stories, new or old. Alice can also specify that she wants to observe only actions that include a particular keyword, actions occurring only in particular categories or subcategories, etc. Alice can also specify particular stories she wishes to monitor, such as by selecting a link on the page's permalink that reads, “add this story to my incoming view.” Alice can also “pin” the stories shown in interface 850. When she hovers her mouse over a particular story shown in interface 850, one element that is revealed is a pushpin icon which, if selected, causes the story to remain in region 886 of interface 850, and/or be added to a list of favorites (878).

A variety of graphical tools are shown on the left hand side of interface 850. They include charts of information such as which stories in the last hour have been most popular 876, the relative rankings of stories that Alice is monitoring (has pinned) 878, a more comprehensive view (i.e., including information predating Alice's current interactions with interface 850), etc. At 872, the story entry 170 of a story that Alice hovers her mouse over, such as story 854, is displayed and she can interact with the story entry 170 such as digging it or burying it accordingly.

FIG. 8C illustrates an embodiment of a visualization interface. In the example shown, a user may switch between different visualization styles (e.g., implementations of “stack” and “swarm”) by selecting from among choices provided in region 888. The visualization shown in FIG. 8C has multiple modes which can be selected from in region 889. When “all activity” is selected, all preference events occurring in all areas are included in the visualization. When “popular stories” is selected, stories that have been promoted to the front page are shown, arranged in the order in which they were promoted. When “upcoming stories” is selected, the most recently submitted stories are shown. In some embodiments, information such as a color scale is used to help depict when newly submitted stories have associated preference events. For example, if a newly submitted story has twenty or more diggs, the representation of the story may be colored bright red, indicating that the story is rapidly gaining interest.

The interface shown in FIG. 8C also includes a region 893 in which a user may select between seeing a visualization depicting the activities associated with individual stories (by selecting “Stories”) or by seeing a visualization depicting the aggregated activities associated with the categories to which stories are assigned (by selecting “Topics”). In the example shown in FIG. 8C, the “Topics” view is selected, and the preference events being visualized are shown relative to the topics rather than individual stories.

The interface shown in FIG. 8C also includes pause (890) and zoom (891) controls. The current amount of zoom is indicated in region 892. By using zoom control 891, groups of stories (e.g., the most recent stories) can be focused on, or the visualization can be pulled back for a broader view. Pause control 890 can be used, for example, to assist in more readily focusing on a specific story when a great deal of activity is occurring and the visualization would otherwise change rapidly. When in the “popular stories” mode (889), the zoom control can be used as follows. If the visualization is zoomed all the way out, the user is able to see the n most recently promoted stories, and get a sense of which stories continue to have a significant amount of associated preference events, even if they are no longer on the front page. The visualization provides information on which stories are active, even if they were not recently submitted. The value of n can be configured by the user and/or by a site administrator. An example default value of n is 100.

FIG. 8D illustrates an embodiment of a visualization interface. In the example shown, Alice has selected a story from a stack visualization interface, such as by clicking on one of the stacks shown in FIG. 8B (e.g., 884 or 856). In doing so, Alice is presented with additional information about that story, such as who dugg it, how many comments it has, etc. Links to the permalink page, etc., are also provided. In the example shown in FIG. 8D, a sparkline-style graph is also provided that shows a more detailed hour-by-hour display of activity on that story, including the frequency and magnitude of preference events. In various embodiments the information shown in interface 894 is configurable. For example, while a default view may show the last 48 hours of activity, the user (or an administrator) may be able to specify additional ranges, and/or the default range may be selected based on how much activity associated with the story has occurred. For example, a story with a lot of recent preference events may default to a 12 hour range, while an old story may show a histogram of all activity over all time.

FIG. 9 illustrates an embodiment of a visualization interface. The example shown is an implementation of a portion of website 116 as rendered in a browser. In this example, interface 900 is configured to present a visualization of the genealogy of the diggs (also referred to herein as a “tree view”) of a story on preference system 102.

In the example shown, story 902 was originally submitted by the user David. When he successfully submitted the story, it appeared in his profile, as well as in the Friends History (e.g., at 610 of FIG. 6) of the several people who have listed David as their friend. Suppose ten people have David as a friend, including users 904, 908, and 912 and seven users not pictured. After David submitted the story, friends 904, 908, and 912 dugg story 902, either through their own friends pages, or through David's profile. They are displayed in interface 900 as connected to David. Users who have David listed as a friend who did not digg the story are not displayed in interface 900. Users 906 and 910 do not have David as a friend, but dugg the story through visiting his profile. As a result, they are also shown connected to David.

When users 904-912 dugg story 902, that action was recorded in their respective user profiles as well. Visitors to their profiles, and those who list them as friends who digg the story will be shown connected to them, the way they are shown connected to David. If expansion tab 914 is selected, interface 900 will continue to provide detail down the tree (those who dugg story 902 through user 916, and so on).

One use of the tree view is that users can trace how their friends learned about stories and meet new friends. For example, if Alice notices that Bob diggs a lot of cryptography stories, she can determine where Bob diggs them from—does he submit the stories himself, or is he mainly digging stories submitted by CharlieB—and add new friends (such as CharlieB) as appropriate.

FIG. 10 illustrates an embodiment of a visualization interface. The example shown is an implementation of a portion of website 116 reached by selecting region 186 of FIG. 1B as rendered in a browser. In this example, Alice is viewing upcoming stories, which may be displayed in a variety of ways. If she selects region 902, Alice will be presented with upcoming stories in a format similar to that shown in the story window 164 shown in FIG. 1B (including one or more story entries 170). In the example shown, Alice has selected to view the upcoming stories in a cloud view by selecting tab 904. In this view, the title of each story in the upcoming queue is visualized as a function of the number of diggs it has. Stories with few diggs are shown in a very small font, and may be colored in a subtle manner, such as by being displayed in grey. Stories with many diggs are shown in a very large font and may be displayed in another color, such as red or black. Stories dugg by friends are also shown in a different color, such as green, irrespective of number of diggs. In some embodiments, additional information is received from the interface shown in FIG. 10 by taking an action such as hovering a mouse over a story title. In such case, information such as the current digg score of the story, which if any friends have dugg the story, and/or the story entry 170 of FIG. 1B is shown.

Which stories will appear in the cloud view can be configured, such as by selecting one or more categories to view or limiting the view to stories dugg by friends. The cloud view can also be sorted by a variety of factors. As shown, the newest (most recently submitted) stories are shown at the top, and older stories are shown at the bottom of FIG. 10. If the stories were sorted by most diggs, then stories rendered in the largest font would appear first and stories rendered in the smallest font would appear last. Other sorting methods may also be used, such as by sorting by most or least comments.

FIG. 11A illustrates an embodiment of a visualization interface. The example shown is an implementation of a portion of website 116 reached by selecting the appropriate portion of region 188 of FIG. 1B as rendered in a browser, and is an example of a swarm interface (also referred to herein as a “swarm visualization”). In this example, Alice is viewing upcoming stories. Users are shown represented by their avatar icons, or by more generalized shapes. As they digg a story, their icon is shown “swarming” around the story in real time—the avatar moves near the story the user is digging, as do the avatars of the other users currently digging the story. In some embodiments, the size of the user's avatar (or other representation of the user) increases and decreases based on the number of stories they are currently digging.

In some embodiments, only recent activity is shown—such as diggs in the last 10 minutes. Stories with more activities (such as diggs and comments) will appear larger than stories with fewer activities. In some embodiments, additional information is received from the interface shown in FIG. 11A by taking an action, such as hovering a mouse over a story title. In such case, information such as the current digg score of the story, which, if any friends have dugg the story, and/or the story entry 170 of FIG. 1B is shown. The links between stories can also be shown, indicating, for example, that several of the same people that dugg a particular first story also dugg a second story, by connecting the two stories with a line. Indicators such as the color or width of the line can show how strong or weak the connection is between the stories.

FIG. 11B illustrates an embodiment of a visualization interface. The example shown is an implementation of a swarm visualization. In the example shown, stories are represented as circles, with the title of the story in the center of the circle. Users “swarm” around the stories when they indicate a preference for the story, such as by digging it (and/or commenting on it, as applicable). Every time a story is dugg, the story's circle increases in size. Thus, the bigger the circle, the more active the story is. In the example shown, story 1130 is very popular, while story 1132 is less popular. Story 1134 has very few associated preference events.

As users digg more stories, they move from circle to circle, and also increase in size. For example, a very large user might represent a person who is not taking much time to read stories, but is instead merely rapidly indicating preferences. In the example shown in FIG. 11B, the user “Bob” (1136) has recently indicated preferences for many stories, while other users (e.g., user 1138) are less active. In the example shown, stories are initially randomly placed within the interface. As preference events associated with the stories occur, their positions change depending on who is digging (commenting, etc.) on them. For example, stories that are closer together indicate that they are being dugg by the same users, and by hovering a mouse over the story, such connections between stories are revealed.

Different modes of the swarm visualization may be presented by selecting one of the options in region 1140. For example, if the “all activity” is selected, circles representing stories and diggers are quickly removed from display if no associated preference events are occurring/being made, respectively. When the “popular stories” mode is selected, the display is initially loaded with the n stories most recently promoted to the front page. As new stories are promoted, they appear in the visualization, and the (n+1)th story is removed. The value of n may be configured, e.g., by a user or an administrator. In some embodiments n is 35. When the “upcoming stories” mode is selected, the n most recently submitted stories each receive a circle. In some embodiments n is 30.

FIG. 11C illustrates an embodiment of a visualization interface. In the example shown, Alice has selected a story from a swarm visualization interface, such as by clicking on one of the story circles shown in FIG. 11B. In doing so, Alice is presented with additional information about that story, such as who dugg it, how many comments it has, etc. Links to the permalink page, etc., are also provided.

In the example shown in FIG. 11C, the lines between stories indicate common diggers between those stories. The more diggers in common that a story has, the thicker the line. For example, story 1150 and 1152 have considerably more common diggers (as indicated by line 1156) than story 1150 and 1154 do (as indicated by line 1158).

Alice may also override the default amount of time a particular story will be displayed in (e.g., in the interface shown in FIG. 11B) by selecting either region 1150 or 1162 of the interface shown in FIG. 11C. Thus, for example, to prevent story 1150 from being removed when a new story is displayed, Alice may select region 1160. To immediately remove the story from the interface irrespective of when it might otherwise have been removed, Alice may select region 1162.

Additional Embodiments

In some embodiments, a plugin and/or add-on to a computer program product is used to provide digging (and/or burying, commenting, and submitting) functionality. The plugin/add-on is associated with an interface to server 102 which may include functions that determine whether a permalink already exists for the submission, and invoke processing of a new submission, a comment, etc., as appropriate.

For example, a plugin to a web browser (e.g., a Firefox extension) can be configured to offer a user the ability to digg an item directly from the context in which it is encountered without having to visit the submission interface described in conjunction with FIG. 3 or a permalink such as the one shown in FIG. 4. For example, a notification embedded in a page or overlayed such as by the browser can indicate whether the page a user is currently browsing has been submitted as a story contribution yet. If not, a user can interact with the notification, such as by clicking on an interface that reads, “this page has not yet been submitted to digg.com, submit it now.” Similarly, if the page has already been submitted, such as by a different user, the notification may take a variety of forms, such as an overlay of the current digg score (172) and a digg box, or a change, for example, in the background color, or some other element of the page.

Configurable dropdowns and/or overlays can also be provided to alert a user of certain activity. For example, the user can set an alert to receive notification when new stories having certain keywords are submitted to server 102. Notification can also be provided for friends' digging activities as they occur, such as that a friend has just dugg a story or commented on a product.

As used herein, content contributions are pointers to content (e.g., news articles and podcasts) that is stored outside of preference system 102, typically by a third party. In some embodiments, users submit the content itself (e.g. the full text of articles, and the audio file) rather than or in addition to a pointer to the content, and the techniques described herein are adapted accordingly. The terms “content,” “content contribution,” and “pointers to content” are used herein interchangeably. As described in more detail below, content contributions are not limited to news articles. Other content (such as products, services, songs, sounds, photographs, and video) can be submitted, dugg, buried, and commented on and the techniques described herein can be adapted as appropriate. Preference events taken on those types of content may likewise be associated with a profile and shared with friends in a manner similar to that described, for example, in conjunction with FIG. 6.

FIG. 12A is an example of a content contribution. The example shown represents a restaurant submission. The name of the restaurant (1200) is included, as is information such as who submitted the restaurant, the URL of the restaurant, the type of cuisine it serves (1202), and the general location of the restaurant (1204). Users may perform such actions as searching for restaurants by cuisine type and/or location, and limiting results to ones having a threshold number of diggs. Restaurants having no or few diggs can be displayed as “upcoming restaurants,” separated from “promoted restaurants” which have digg scores exceeding a threshold. Users can also supply additional information about their preferences for the reference, such as by supplying one or more tags (1202) that indicate attributes such as “ambiance” or signature dishes. As described in more detail below, which fields/tags are collected at submission time (and which, if any, can be added subsequently) and shown can be configured as appropriate depending on the type of content. For example, in the case of a product, a stock photo of the product may be included.

FIG. 12B illustrates an embodiment of an interface to a preference system. In the example shown, the interface unifies a user's preference for things across multiple genres of content. For example, the user can digg for news (1250), videos (1252), and restaurants (1254) all through the same interface. As described in more detail below, the friends features described above can also be used in conjunction with other types of content contributions. For example, using the interface shown in FIG. 12B, a visitor to Alice's profile can learn which news stories she's been digging as well as learn which restaurants she diggs or doesn't digg. Similarly, Alice can customize the views of each of the tabs (1250, 1252, 1254) to display only restaurants her friends of agreed on, restaurants nearby (e.g., by selecting a region on a map or entering a ZIP code) that at least one friend has dugg, etc.

FIG. 12C illustrates an embodiment of an interface to a preference system. In the example shown, digging functionality has been combined with mapping functionality. When a user searches a map, such as a web-based map service, for nearby restaurants, entries on the map include an indication of the number of diggs a business has had and the ability to digg or comment on the business directly from the map interface.

FIG. 13A illustrates an embodiment of an interface to a preference system. The example shown is an implementation of a portion of website 116 which includes the ability to submit, digg, and comment on products (including software), as rendered in a browser. In this example, Alice has selected to view products agreed on by her friends (1322).

Alice can submit a new product review by selecting portion 1302 of interface 1300. She can view products in one or more categories by selecting the appropriate portion of region 1304. Portion 1306 of interface 1300 displays the recent activities of Alice's friends in a dashboard format.

Region 1326 of interface 1300 indicates that four of Alice's friends have dugg product 1324, the ACME MP3 player. Alice can also see which of her friends have dugg product 1324 by hovering her input device over the digg score box of product 1324. In some embodiments, Alice can interact with region 1326, such as by being presented with a dialogue that offers to send an email to all of her friends listed in the region. In some embodiments, additional actions can be taken with product 1324. For example, Alice may be presented a “buy this product now” icon or link.

All of the views shown in FIG. 13A can be syndicated as RSS feeds by selecting RSS link 1320 on the appropriate page view. For example, if Alice is a professional critic, users and those who choose not to use web site 116 on a regular basis can syndicate comments that she makes on products, etc.

In some embodiments, profile visitors (including Alice) are presented with the option to search (1308) all of site 116 for product keywords (1310), search Alice's diggs for product keywords (1312), and/or search diggs made by Alice's friends for product keywords (1314). For example, a visitor to Alice's profile can search for MP3 players that she has dugg or commented on. In some embodiments, search interface 1308 includes the ability to filter results on meta information such as regions for DVDs, languages for books, etc. In some embodiments, views (and searches) can be limited by other factors, such as location (distance from Alice), availability (whether a product is in stock and how quickly it can arrive), etc.

FIG. 13B illustrates an embodiment of an interface to a preference system. The example shown is, as rendered in a browser, an implementation of a portion of website 116 that includes the ability to submit, digg, and comment on products. In this example, Alice has selected to view products in the category, MP3 player, from a larger set of categories, such as those listed in region 1304 of FIG. 13A.

In the example shown, each product listing (1302, 1304) includes a photograph of the MP3 player (1306), as well as a digg score/digg box (1308), title, description, etc. (1310). The MP3 players shown in this example are sorted by popularity.

On the right hand side are assorted graphs (1312, 1314) of information associated with the products shown. Graph 1312 compares the popularity (e.g. digg scores, number of comments recently made, etc.) of different MP3 players against each other over time so that trends such as which ones are gaining in popularity and which ones are decreasing in popularity can be visually determined.

In the example shown, the Acme F242 player is more popular than the Beta 10 player. In some embodiments, the frequency with which a user visits preference system is considered when determining the popularity of a product. For example, suppose the Beta 10 player has 165 diggs, 25 of which were made by users who have not visited the preference system in 3 months. In some embodiments, the diggs of those 25 users are expired. The product will remain listed in the absent user's profiles, but their diggs will not be included when calculating the popularity of the product.

Users also have the ability to undigg a product to indicate that they've moved onto something new. For example, suppose Alice currently has a Beta 10 player and is interested in upgrading. If she purchases an Acme F242, she can visit her profile to undigg the Beta 10 and digg the Acme F242. Her actions—undigging the Beta 10 and digging the Acme F242 instead—will also be reflected in graph shown at 1312. For example, on the day that she undiggs the Beta 10, its position along the vertical axis will be decreased. On the day that she diggs the Acme F242, the Acme F242's position on the graph will similarly increase.

Graph 1312 also includes indications of the individual users who are taking digging and undigging actions. For example, when Alice hovers her mouse over region 1318, she can see that a user, Mark, dugg the Acme F242. Indications of actions taken by her friends are also included on graph 1312. For example, regions associated with friends' diggs of the Acme F242 are highlight in green, or with avatars, or other indicators that her friends have indicated preferences at a particular time. For example, Alice can use graph 1312 to determine that David dugg the Acme 242 two months after Charlie dugg the Beta 10.

The information shown in FIG. 13B can also be generated based on one or more searches in addition to or instead of tabbed browsing. For example, Alice could perform a search of “popular MP3 players at least one of my friends owns” and see the information shown in FIG. 13B as a result.

In some embodiments, demographic information is displayed. For example, in graph 1314, the popularity of a particular MP3 player is broken down by assorted groups such as teens and adults, or girls and boys. Demographic information can similarly be included in a search so that, for example, a parent shopping for a present for his or her child can locate the “hottest MP3 players among teenagers this week,” and the “most popular movie for women aged 20-30,” through a search interface configured to accept such queries.

FIG. 14 illustrates an embodiment of an interface to a preference system. The example shown is an implementation of a portion of website 116 which includes the ability to submit, digg, and comment on photographs and video, as rendered in a browser. In the example shown, photograph 1402 was dugg by a friend, as indicated by banner 1404. By selecting digg box 1406, a visitor can indicate a preference for the photograph shown. In some embodiments, visitors indicate their preference for content such as video 1408 by selecting an icon such as icon 1410.

The content shown in interface 1400 can be presented in a variety of ways. For example, video content may be represented as an icon, such as the filmstrip icon shown at 1408. A screen shot of the first frame of the video may also be shown, and interactions, such as hovering a mouse over region 1408 could trigger actions such as causing the video to be played in the browser.

In some cases, it may not be possible to embed the content directly into the interface shown in FIG. 14. In such a case, the video is shown in a format similar to story entry 170 (1416), and a preview button 1414 is included. When preview button 1414 is selected, a video player 1412 automatically slides out in which the video can be displayed.

Permalink pages such as the one shown in FIG. 4 can be adapted for photograph and video content as appropriate, and users may comment, blog, and take other actions with respect to visual and other content (such as songs) as appropriate.

Cohort Detection

A nefarious individual may create multiple personas all under his control or offer money to other users in exchange for their complicity in digging stories. A group of users (e.g., in the same dorm, company, or other organization) may attempt to digg stories favorable to that entity, etc. Groups of users banding together in such a fashion are referred to herein as “cohorts” and “associates” interchangeably.

In some cases, cohorts may be “friends” on the site, with profiles linked to one another and may visit each other's profiles and click on all of their friends' stories. Cohorts may also organize in a more clandestine fashion, relying on tools such as instant messages and email (e.g., out of band) to agree to digg one another's stories so that they are promoted (e.g., reach the front page) sooner. In some cases, at least some cohorts may be acting subconsciously or otherwise be innocent. For example, a user, “FanBoy” may always digg the posts of a user, “RockStar,” without ever reading them, because FanBoy likes RockStar and wants to see RockStar's submissions always be promoted, irrespective of their merit.

In general, typical users making typical use of “friend” features may legitimately visit their friends' profiles and digg some of the stories their friends have dugg. Legitimate friends typically do not digg one another's stories in an orchestrated, continual fashion. As described in more detail below, a variety of techniques can be employed to detect the activities of the aforementioned “digging associates,” and to lessen the impact of concerted digging and group/friend-think on the promotion of content, while not penalizing legitimate friend-related activity.

FIG. 15 is a flow chart illustrating an embodiment of a process for detecting associates. In some embodiments the process shown in FIG. 15 is performed by cohort detection module 120 and promotion engine 118 working in conjunction. The process begins at 1502 when a plurality of indications of preferences for a content item is received from a plurality of users. Typically, the processing performed at 1502 occurs over a period of time. For example, suppose a user, Bob, submits a story to preference system 102. Alice diggs it a few minutes later, a user, Charlie, diggs it a few minutes after that, and so on. Bob's submission and Alice and Charlie's diggs, collectively, are received at 1502.

At 1504, the preference events received at 1502 are accumulated. For example, in some embodiments, information stored in database 112 is accessed and all of the preference events associated with the story submitted by Bob are retrieved. In various embodiments, the processing performed at 1504 executes as part of a batch process. At 1506, associated events are detected. Several examples of ways in which associated events (e.g., events submitted by cohorts) can be detected are described in more detail below. At 1508, the effect of the associated events is reduced, prior to assigning a status to the item. For example, prior to determining that content should be promoted, the effects of associate digging are removed. As another example, the effects of cohort burying are removed prior to determining that content should be removed (e.g., so that legitimate content is not removed).

In some embodiments, cohort detection is performed as follows. Once a week, the preference events for the preceding week are retrieved from database 112 and evaluated. In some embodiments the entire store of preference events for the time period (e.g., week) is evaluated. For efficiency, evaluation may also be limited to include just the behavior of friends, to include only preference events associated with unpromoted content, etc.

A list of cohorts is determined and stored in database 112. When determinations about the promotion (and/or removal) of candidate content are made for the following week, the list of cohorts is consulted. For example, if cohort digging has been detected for a particular item, the impact of the cohort digging is reduced. One example of such a reduction is by discarding from consideration the digg counts provided by the detected cohorts. Another example of such a reduction is to increase the number of digg counts required for the content to be promoted. At the end of the week, the cohort list is updated based on the preference events recorded during the week.

Example Groups

Group cohorts are associates that have very common habits. One example is users that bond over a particular micro-community or area of interest. People who are intensely in favor of a particular political candidate, or those passionate about a niche technology market, or live on the same dorm floor are examples of users that might form groups. Typically, those users are seemingly random users (with different IP addresses—that log in at different times of the day, etc.) who have a very high correlation factor of the stories they digg on a regular basis.

Two or three or four users could in fact randomly happen to digg the same two or three stories, however for a larger group to digg a larger number of stories in common, a statistically probable correlation between their digging activities may be sufficient to mark those users as group diggers. Multiple techniques can be used to detect groups of diggers.

Suppose that cohort detection includes evaluating, for each user, the behavior of that user's friends. In this example, suppose Alice has ten friends and has dugg (or submitted) a total of twenty stories in the last week. In such a scenario, at 1504, the preference events of Alice's friends with respect to those twenty stories are evaluated. For each of the twenty stories dugg/submitted by Alice, a count is made of the number of Alice's friends that also dugg that story. The first story was dugg by three of her friends (Charlie, Dan, and Eve). The second story was dugg by five of her friends (Charlie, Dan, Eve, Joe, and Ted). The third story was dugg by two friends (Dan and Eve), and so on, with the twentieth story being dugg by eight of Alice's friends. In some embodiments the “Agreed Upon” feature is used in conjunction with the processing shown in FIG. 15.

Stories with a high number of common friends might indicate cohort behavior with respect to those stories. Variables such as how many friends need to agree across how many stories are configurable. The variables may also be dynamic and depend on context such as the category of the story, or—in the case of other content—the type of content. As one example, a rule may be specified that if a group of the same 50% of a user's friends agree on 20% of a user's submissions/diggs, that group is a cohort group and its diggs should not be counted in content promotion evaluations. In Alice's case, if 5 of her friends agree on 4 or more stories, those 5 (or more) friends' diggs, as well as Alice's, will not be counted. An evaluation of Alice's friends' activity for the week indicates that Dan and Eve routinely digg the same content that Alice does—and that if Alice has dugg a story, and Dan and Eve have also dugg that story. However, since Dan and Eve represent only two of Alice's ten friends, no cohort group will be designated for Alice, Dan, and Eve.

In some cases a user may belong to multiple groups. For example, suppose Alice has an agreement with her friends that she will digg all of their stories if they digg hers. She also has an arrangement with a political party that she belongs to that she will always promote stories that are favorable to a particular candidate (irrespective of who submitted the story). Suppose there are 200 members of the political party on the site. Only some subset of those members may be detected as being cohorts (i.e., the ones who digg frequently). Nonetheless, by detecting the collective behavior of that subset, the stories about that candidate are less likely to be promoted due to Alice and her cohort's activities than the activities of average users.

Another example of a technique for detecting cohorts follows. A table of activity for a time period is constructed in which users form the x axis and stories (or other content) form the y axis. For example, users active over the last 7 days and the stories promoted over the same time period are used as the respective axes. Each cell in the table is populated with information indicating, e.g., the friends of the user that also dugg that story. In some embodiments the cell is populated with all of the other individuals that dugg that story irrespective of friend status. Clustering techniques can then be applied to determine, for a given row, whether there are other users that consistently appear. Suppose out of the 20 stories Alice dugg, the digging history of 10 of those stories shows that in addition to being dugg by Alice, users A2, A3, A4, A5, A6, and A7 also dugg each of those 10 stories. A cohort group consisting of Alice and users A2-A7 can be formed and stored. As part of the promotion evaluation process (described in more detail below), each of the diggers of that candidate story is checked to see if that user is present in the cohort table. If so, it is determined whether any of that cohort's cohorts have also dugg the story. If so, a threshold is applied, and it is determined whether cohort behavior is indicated or not. For example, suppose Alice diggs story S5. The users A2, A3, A5, A6, and A7 have also dugg story S5, but user A4 has not. This likely indicates cohort behavior because all but one of the members of a cohort group have been detected as having dugg the same story. Suppose now that Alice diggs story S6 and only A2 and A7 digg it. In this case, cohort behavior (on the part of Alice and the rest of the A2-A7 group) is not likely present. The process is repeated for other cohort groups. And, for example, it may be determined that another group (e.g., including a different group of users) is implicated by using the techniques above.

Suppose Alice is determined to be a member of three cohort groups. The first group consists of Alice and users A2-A7 as above. The second group consists of Alice and a second set of users, and the third group consists of Alice and a third group of users. Now suppose a story S7 is otherwise able to be promoted and is being evaluated for cohorts. Each of the diggers of the story is searched for in the cohort list. If none of the diggers is present in the cohort list, the story may be promoted. Suppose Alice dugg story S7. It is determined that Alice is in the cohort database. Suppose user A2 dugg the story, but none other of the first group (Alice and A2-A7) dugg the story. A collective action on the part of Alice's first group is not implicated because an insufficient number of group members (e.g., compared to a threshold) dugg that story. In some cases the threshold required is all of the members of Alice's group. In other cases, a looser match may be performed against Alice's group members, e.g., to accommodate situations such as where one or two of the group members is out of town (and will not be digging as a cohort) when all the other members do. The rest of Alice's groups are also checked—and, if a threshold number of members in either of her other groups also dugg story S7, their collective action can be mitigated accordingly.

In various embodiments, the cohort groups listed in the cohort table is periodically updated to prune and add new groups. In some embodiments the updates are performed across all data, across data that is new since the last time cohort groups were detected, or using a rolling sample of data.

In some embodiments a pool of candidate cohorts is maintained and additional candidates are include or rejected from the pool. For example, suppose Alice dugg 25 stories during a sample time period. For each of the other users that were active during that time period, a tally is made of how many stories each of those users had in common with (also dugg with) Alice. The tally is sorted and users with tallies exceeding a certain threshold are designated as cohorts of Alice (assuming she has any).

The technique can also be used to recommend other stories, by finding other users who have an overlap of stories dugg (and therefore a “high” correlation factor).

In various embodiments, genetic algorithms are used to determine groups of cohorts.

Example Weighting a First User's Agreement with a Second User

The following is an example of a technique for addressing the blind following of one user by another. In the technique, each subsequent digg by a user, to another user's submitted stories, within a time period, is made to be valued less (e.g., less than one vote, and/or as a reduction to the “user reputation score” discussed in greater detail below). For example, within a time period (e.g. 30 days), each subsequent time that Alice diggs one of Bob's stories, Alice's digg is attributed progressively less value. The first time Alice diggs a story submitted by Bob, within a rolling 30 days, it's worth one point (or, other full value ascribed to Alice). The second time Alice diggs a story submitted by Bob, that second story receives a lower score. The third time Alice diggs a story submitted by Bob, that third story receives an even lower score. If Alice diggs many of Bob's submissions during the 30-day period, it is possible that some of those stories may receive zero value from Alice. Any other stories dugg by Alice, and not submitted by Bob, will receive Alice's full value.

Example IP Address

In various embodiments, preferences indicated for the same content by users that share an IP address are counted less and less, e.g. using a variant of the technique described above. In the modified technique, the first digg from the IP address for a particular content is given a full count. Each subsequent digg from the same IP contributes exponentially less toward promotion. In this scenario, users creating multiple accounts and using them from the same machine, and users from the same company or school digging the same content will require greater diversity. However, the activities of two users legitimately sharing the same computer will typically still count, in full, toward the site.

Example Statistical Analysis

Yet another way of performing cohort detection is to examine every content item, and every preference event for that item, and to compare the results to all other content items to determine how much overlap/how many diggers they have in common.

Suppose a first story (that has 10 diggs) is compared to a second story (that also has 10 diggs). The two stories would have a 100% correlation factor if they were dugg by the exact same set of 10 users. If the two stories had nine diggers in common, the story still likely indicates group behavior, whereas if the two stories had four diggers in common, autonomous decisions on the part of the diggers are likely to have been made.

Correlation factors can be calculated a number of ways including standard similarity factors used in mathematics such as Jaccard similarity coefficients and the Jaccard distance between two sets of items. For example, A and B can be represented by two different user's sets of diggs over a given timeframe. The following algorithm computes the Jaccard distance—or similarity factor between two user's digging patterns:

${J_{\delta}\left( {A,B} \right)} = {{1 - {J\left( {A,B} \right)}} = {\begin{matrix} {{{A\bigcup B}} - {{A\bigcap B}}} \\ {{A\bigcup B}} \end{matrix}.}}$

Once all correlation factors are calculated for how a particular story overlaps with every other story, a normal standard deviation breakdown of the correlation factors can be determined. The majority of stories are likely to fit inside the middle of the bell curve, while one or two standard deviations out would represent some highly correlated stories. In some embodiments, stories more than one standard deviation out indicate group digging behavior for stories over a minimum threshold (e.g., 20 diggs).

Promoting Content

As mentioned in conjunction with FIG. 1B, a variety of techniques can be used to determine when content, such as a story, should be “promoted” out of the upcoming area or similar area and shown on the main page or other appropriate location.

FIG. 16 is a flow chart illustrating an embodiment of a process for promoting content. In some embodiments the process shown in FIG. 16 is performed by promotion engine 118. The process begins at 1602 when one or more candidate content items is determined. For example, at 1602, all of the items in the upcoming stories pool might be selected. Optional pruning of the candidates may also be performed at 1602. For example, stories more than 48 hours old, reported as violating a term of service, or otherwise meeting pruning criteria may be removed from the set of candidate content items at 1602.

At 1604, user reputation scores are received, such as from database 112. A user reputation score approximates how good a particular user is at submitting and/or locating “good” content, and in some embodiments how good a particular user is at identifying “bad” content. One way of determining a user reputation score for a particular user (e.g., Alice) is as follows. Each time Alice diggs a story in the upcoming story pool that is subsequently promoted, Alice's user reputation score is incremented by a fixed value. Each time Alice burries a story in the upcoming story pool that is subsequently removed from the pool, Alice's user reputation score is also incremented by a fixed value. In some embodiments multiple user reputation scores are maintained for Alice, e.g., with one relating to her success at digging stories and another relating to her success at burying stories. Alice may also have different user reputation scores for each category or type of content, for example, to reflect that she is astute at selecting sports related stories for promotion, but not very good at selecting photographs that are ultimately promoted.

As another example, whenever a story is promoted, each of the users that dugg that story (also referred to herein as having “voted” for the story) prior to the story being promoted receives a fractional share of the fixed value, added to their respective user reputation scores. The score of the original submitter is, in some embodiments increased by a higher fixed value than those that digg the story—in other embodiments the submitter is treated as being the first digger of the story. As another example, the first n users who digg a story, or any users who digg the story within n amount of time from when the story is submitted, have their user reputation scores incremented while later digging users do not, irrespective of whether the later digging users dugg the story prior to its promotion. The scores may be updated by an equal value, or may take into account the timing of the diggs. For example, the first person to digg a story that is ultimately promoted may receive a higher increase to his user reputation score than the fifth digger, who also receives an increase to his score. In various embodiments, only stories dugg in the last 30 days or some other time are considered when determining user reputation scores. Additional techniques for determining a user reputation score are described in more detail below.

At 1606, a content reputation score is determined for each item in the group of candidate content items. One way of calculating a content reputation score is to sum the user reputation scores of each of the users that voted (or dugg) the story. In various embodiments, the user reputation scores of some users is not considered at 1606. For example, users that have recently registered may not have their user reputation scores be used in any computations until two weeks have elapsed.

At 1608, a determination is made as to whether or not the content should be promoted. For example, at 1608 the content reputation score for each candidate content item is compared against a threshold. If the threshold is exceeded, the content is promoted. If some of the content reputation score is determined to include cohort digging, the threshold is raised, or the score attributable to the cohort digging activity is discarded, as applicable. In various embodiments, additional checks and/or throttling are performed at 1608. For example, promotion engine 118 may be configured to perform the processing shown in FIG. 16 as a regularly occurring batch process. For any particular iteration of the process, a limit may be imposed by promotion engine 118 on the number and/or nature of content that can be promoted. For example, promotion engine 118 may be configured with a rule that only five images may be promoted per execution of the process, that a maximum of one story per category may be promoted, or that a total of ten items may be promoted per cycle, across all content.

In some embodiments content items that are otherwise promotable (e.g., that have content reputation scores exceeding the appropriate threshold) are sorted based on the ratio between their respective content reputation scores and the applicable threshold values. The ratio (e.g., the sorted list) is used as tie breaker information in the event that more content is promotable than the rules allow to be promoted. In some embodiments, promotable items that are not promoted are considered for promotion on the next iteration of the process shown in FIG. 16. In other embodiments, promotable items are placed in a queue and released from the queue after a period of time has elapsed. In some embodiments all promotable items are placed in a queue prior to promotion so that an administrator has time to review the content for violations of service terms or other reasons.

In some embodiments different thresholds are used for determining whether to promote content in different categories and/or content of different types. For example, a higher threshold may be used for the promotion of sports news than for the promotion of astronomy stories. Additionally, multiple thresholds can be employed when determining whether to promote a particular content item, such as requiring that a total digg count threshold be exceeded for the story, along with the content reputation threshold. In the event that a total digg count is considered, in some embodiments the total digg count for the story is evaluated at 1602 as part of the initial candidate selection.

Yet another technique for calculating a user reputation score is as follows. Let u be a user, Iu be the set of content dugg by the user in the last 28 days, Pu be the subset of items in Iu that were promoted and for which the user was an “early” digger, and Di be the current digg total of item i. The user reputation score (su for the user u can be expressed as:

$s_{u} = {\frac{\sum\limits_{i \in I_{u}}D_{i}}{{I_{u}} + 30}.}$

The number 30 in the denominator is a regulator that compensates for issues such as when a new or inactive user diggs an item which subsequently becomes very popular. It regulates exceptionally high user reputation scores that could otherwise result. In various embodiments, the total number of diggs made by a user are considered when determining a user reputation score so that an indiscriminate digger cannot achieve a high user reputation score by merely digging every single story in the upcoming pool.

Automatically Adapting Thresholds

In some embodiments, promotional requirements (e.g., the amount of the content reputation score and/or total digg count) are dynamically adapted and the corresponding thresholds are raised and lowered based on a variety of factors. Thresholds can be automatically recalculated, e.g., once a day, once a week, once a month, based on historical information. Examples of factors include:

1. An assessment of diversity of digging in a given topic. Diversity can be a measurement of many things. One example is the location of the digging activity within the site, such as on a permalink page vs. from users' friends profiles. Other diversity examples include same-IP and other cohort-related information. Diversity can be required so that if something is insufficiently (sufficiently) diverse, the bar for promotion for a given story can be raised (or lowered) accordingly.

2. The velocity at which diggs are received for the content.

3. The total number of visitors to a given topic (e.g., based on a trend of historical data in the topic and/or relative to other topics). For example, during annual sporting events, during elections, etc., a surge of interest in a topic should typically require an increase in the requirements for a story associated with that event to be promoted. At other times of the year, considerably fewer visitors are likely to review content associated with the topic and the threshold will adjust downward accordingly.

4. Activity during specific times of day (e.g., requiring fewer diggs at 3 am Pacific on a Saturday/Holiday than at 11 a Pacific on a Monday). This can also be based on peaks and valleys in site traffic, rather than or in addition to precise times of day (e.g., clock values).

5. The likelihood of a story being promoted given the submitter's history and the distribution and reach of his/her friend network.

6. The number of burries against the content. A story with 25 diggs and 1 bury is promoted, while a story with 25 diggs and 3 buries requires more diggs to be promoted, e.g., exponentially based on the number of burries.

7. If the site has been repeatedly submitted by the same user who submits nothing else.

8. Sophistication of the “average” user interested in the topic. On way of evaluating this factor is as follows. First, “new” users (e.g., those active less than two weeks) are removed. A determination of user reputation scores of all of the remaining users is made and an average is taken. If, over time, the population becomes more sophisticated (higher average), a higher content reputation can be required to promote a story. If the population becomes less sophisticated (e.g., due to a school session starting and many users having joined the system 30 days earlier), a lower content reputation can be required to promote a story.

Thresholds may also be applied selectively to, e.g., different categories, such that Astronomy uses a fixed set of promotion thresholds while Operating Systems is dynamic. Events such as the occurrence of major news events (e.g., an earthquake) can also be used to trigger or disengage the application of dynamic thresholds to categories.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive. 

What is claimed is:
 1. A method of determining whether to promote a content item, with consideration of orchestrated activity regarding the content item, the method comprising: receiving, regarding the content item, a plurality of preference events from a plurality of users; identifying a cohort of users that previously orchestrated preference events for at least one other content item and that includes at least one user in the plurality of users; determining whether the cohort is more likely than not to have orchestrated the plurality of preference events; and determining whether to promote the content item, wherein promoting the content item comprises increasing a prominence of the content item in an interface through which content items are presented to users.
 2. The method of claim 1, wherein a preference event is one of a digg, a bury and a comment.
 3. The method of claim 1, wherein the at least one other content item was submitted by the same user that submitted the content item.
 4. The method of claim 1, wherein identifying a cohort comprises correlating activities of the plurality of users.
 5. The method of claim 1, wherein identifying a cohort comprises: retrieving a list of known groups of associated users; and searching the known groups for the plurality of users.
 6. The method of claim 5, wherein determining whether the cohort is more likely than not to have orchestrated the plurality of preference events comprises: determining whether the same preference event was received from a threshold number of associated users in one group of associated users.
 7. The method of claim 1, wherein identifying a cohort comprises: maintaining a table of known cohorts; and periodically updating the table as additional preference events are received.
 8. The method of claim 1, wherein determining whether the cohort is more likely than not to have orchestrated the plurality of preference events comprises: within the plurality of users, identifying a set of users that submitted the same preference event regarding the content item; and determining whether the set of users submitted identical preference events for a threshold number of other content items.
 9. The method of claim 1, wherein determining whether the cohort is more likely than not to have orchestrated the plurality of preference events comprises: detecting associated events among the received preference events.
 10. The method of claim 9, wherein detecting associated events comprises correlating behavior among the plurality of users.
 11. The method of claim 1, wherein determining whether to promote the content item comprises: increasing a score associated with the content item if it is determined that the plurality of preference events includes multiple negative ratings likely to have been orchestrated by the cohort.
 12. The method of claim 1, wherein determining whether to promote the content item comprises: decreasing a score associated with the content item if it is determined that the plurality of preference events includes multiple positive ratings likely to have been orchestrated by the cohort.
 13. The method of claim 1, wherein determining whether to promote the content item comprises: discarding the plurality of events if it is determined that the cohort is likely to have orchestrated the plurality of preference events.
 14. A system for determining whether to promote a content item, with consideration of orchestrated activity regarding the content item, the system including: a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions that, when executed, cause the processor to: receive a plurality of preference events regarding the content item, from a plurality of users; identify a cohort of users that previously orchestrated preference events for at least one other content item and that includes at least one user in the plurality of users; determine whether the cohort is more likely than not to have orchestrated the plurality of preference events; and determine whether to promote the content item, wherein promoting the content item comprises increasing a prominence of the content item in an interface through which content items are presented to users.
 15. The system of claim 14, wherein the preference event is one of a digg, a bury, and a comment.
 16. The system of claim 14, wherein identifying a cohort comprises correlating activities of the plurality of users.
 17. The system of claim 14, wherein determining whether to promote the content item comprises: increasing a score associated with the content item if it is determined that the plurality of preference events includes multiple negative ratings likely to have been orchestrated by the cohort.
 18. The system of claim 14, wherein determining whether to promote the content item comprises: decreasing a score associated with the content item if it is determined that the plurality of preference events includes multiple positive ratings likely to have been orchestrated by the cohort.
 19. The system of claim 14, wherein determining whether to promote the content item comprises: discarding the plurality of events if it is determined that the cohort is likely to have orchestrated the plurality of preference events.
 20. A computer program product for determining whether to promote a content item, with consideration of orchestrated activity regarding the content item, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: receiving, regarding the content item, a plurality of preference events from a plurality of users; identifying a cohort of users that previously orchestrated preference events for at least one other content item and that includes at least one user in the plurality of users; determining whether the cohort is more likely than not to have orchestrated the plurality of preference events; and determining whether to promote the content item, wherein promoting the content item comprises increasing a prominence of the content item in an interface through which content items are presented to users. 